Skip to content

Conversation

@fern-api
Copy link
Contributor

@fern-api fern-api bot commented Feb 10, 2026

Major refactoring of the upload code system API to simplify the interface and improve consistency. The upload request structure has been consolidated and user ID references have been removed from multiple templates to support a more streamlined architecture.

Key changes:

  • Unified upload request structure with simplified parameter handling
  • Removed user_id fields from chat, workflow, FHIR provider, and other templates
  • Updated upload code system to return asynchronous processing status
  • Consolidated upload request types into a single interface
  • Improved documentation for asynchronous processing workflow

🌿 Generated with Fern


Note

Medium Risk
This is a breaking, SDK-wide generated schema change (v6 major) that alters request/response types for code system upload and removes fields from many response models, which can break downstream consumers and tests.

Overview
SDK v6.0.0 updates the generated TypeScript client to simplify custom code system uploads and remove user_id fields from several templates.

construe.uploadCodeSystem now documents/assumes asynchronous processing (immediate 202 + polling GET /construe/codes/systems/{codesystem} for status), consolidates prior CSV/JSON discriminated request types into a single construe.UploadRequest (with format enum and optional CSV/JSON fields), and expands the upload response to include name and version alongside status. Multiple resource templates (agent chat messages/sessions, workflows, FHIR provider, summary templates, MCP server/tool responses) and wire tests are updated to no longer expect user_id.

Written by Cursor Bugbot for commit be12509. This will update automatically on new commits. Configure here.

Major refactoring of the upload code system API to simplify the interface and improve consistency. The upload request structure has been consolidated and user ID references have been removed from multiple templates to support a more streamlined architecture.

Key changes:
- Unified upload request structure with simplified parameter handling
- Removed user_id fields from chat, workflow, FHIR provider, and other templates
- Updated upload code system to return asynchronous processing status
- Consolidated upload request types into a single interface
- Improved documentation for asynchronous processing workflow

🌿 Generated with Fern
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

export type { GetConstrueCodesCodesystemSearchTextRequest } from "./GetConstrueCodesCodesystemSearchTextRequest.js";
export type { GetConstrueCodesSystemsCodesystemExportRequest } from "./GetConstrueCodesSystemsCodesystemExportRequest.js";
export type { GetConstrueCodesSystemsCodesystemRequest } from "./GetConstrueCodesSystemsCodesystemRequest.js";
export type { UploadRequest } from "./UploadRequest.js";
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Type-only export makes Format enum values inaccessible

Medium Severity

The UploadRequest namespace defines runtime const Format values (Csv, Json), but requests/index.ts re-exports it using export type { UploadRequest }, which strips the runtime value. SDK consumers cannot access UploadRequest.Format.Csv or UploadRequest.Format.Json at runtime — these are effectively dead code. The comparable GetCodeSystemDetailResponse.Status const is properly exported via export * from the types index and works correctly.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants